Repository navigation
Conversation
Documentation build overview
|
|
Thanks for the feedback. I find the rythme of some parts of the text a bit to LLM-isque but if native speakers think it's fine, I'm going to keep it as is. |
|
As said before, the text is principally suggested by an AI and later edited:
|
| * someone, such as the issue's author, already said they would open one; | ||
| * a pull request for the issue already exists. | ||
|
|
||
| In the last two cases, if there has been no activity for a while, ask the |
There was a problem hiding this comment.
I want to say "avoid asking in the issue 'any updates?'" if you're not interested by the feature at all... But I don't know how to say it (which is why I limited myself to the last 2 cases).
For very old issues I think it's better we find them once again if someone submits a newer report or if someone raises the issue again because they encountered the same problem rather than someone wanting to contriubute and randomly picking a very old issue.
|
|
||
| .. _fixing-issues-no-pullrequest: | ||
|
|
||
| Consider whether a pull request is needed |
There was a problem hiding this comment.
The "what is an issue" is in the issue-tracker, but that tracker is in the triage page.
I think it makes more sense to have it with the rest of the issues templates but I (and Claude) wasn't able to find a place in getting-started. So I added this section here.
First draft of issue/PR choregraphy while staying a bit vague. I used Opus 5.5 for the text and reading the existing parts of the devguide and to polish the tone in a more... diplomatic way I would have said.
Once reviews start, I'm going to make the changes manually (likely).